Fast convergence for failures of large scale virtual ethernet segments in evpn and pbb-evpn

ABSTRACT

Systems, methods, and computer-readable media for fast convergence for virtual ethernet segments in EVPN and PBB-EVPN networks are disclosed. A first provider edge (PE) device can receive one or more advertising messages corresponding to one or more virtual ethernet segments, wherein each of the one or more advertising messages can include a port identifier. The first PE device maintains a table including the one or more virtual ethernet segments and the corresponding port identifier. The first PE device can receive a failure message from a second PE device that identifies a first port on the second PE device, and identifies, based on the table, at least one affected virtual ethernet segment that is associated with the first port. The first PE device can remove any routes that are associated with the at least one affected virtual ethernet segment and trigger mass designated-forwarding election for impacted virtual ethernet segments.

CROSS REFERENCE TO RELATED APPLICATION

This is a continuation application of U.S. patent application Ser. No.14/750,311, filed Jun. 25, 2015 (allowed), which is expresslyincorporated by reference herein in its entirety.

TECHNICAL FIELD

The present technology generally pertains to network based services, andmore specifically, to enabling provider edge nodes to perform fastconvergence upon detection of a failure that affects virtual ethernetsegments.

BACKGROUND

Service provider networks frequently provide multiple connections to asingle customer network or customer edge device in order to provideredundancy in the event of a network failure. Unfortunately, a singleport failure (e.g. a Network-to-Network Interface (NNI)) on a ProviderEdge device can affect thousands of associated Virtual Ethernet Segmentsand their corresponding Customer Edge device. Consequently, the timenecessary to activate the redundancy mechanisms for each of the affectedsegments can be significant and result in service interruption.Accordingly, the benefits of redundancy can be significantly limited inmodern service provider networks.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features of the disclosure can be obtained, a moreparticular description of the principles briefly described above will berendered by reference to specific embodiments thereof which areillustrated in the appended drawings. Understanding that these drawingsdepict only exemplary embodiments of the disclosure and are nottherefore to be considered to be limiting of its scope, the principlesherein are described and explained with additional specificity anddetail through the use of the accompanying drawings in which:

FIG. 1 illustrates a schematic block diagram of an example serviceprovider network;

FIG. 2 illustrates an example method for performing fast convergenceupon detecting a Provider Edge port failure;

FIG. 3 illustrates a second example method for performing fastconvergence upon detecting a Provider Edge port failure;

FIG. 4 illustrates an example table for use in performing fastconvergence in EVPN and PBB-EVPN;

FIG. 5 illustrates an example network device; and

FIGS. 6A and 6B illustrate example system embodiments.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationsmay be used without parting from the spirit and scope of the disclosure.

Overview

Additional features and advantages of the disclosure will be set forthin the description which follows, and in part will be obvious from thedescription, or can be learned by practice of the herein disclosedprinciples. The features and advantages of the disclosure can berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. These and otherfeatures of the disclosure will become more fully apparent from thefollowing description and appended claims, or can be learned by thepractice of the principles set forth herein.

The subject technology provides embodiments for fast convergence forfailures of large scale virtual ethernet segments in EPVN and PBB-EVPN.The method includes receiving, at a PE device from a neighboring PEdevice, one or more routing advertising messages corresponding to one ormore virtual ethernet segments. The one or more messages can include aport identifier that identifies the port associated with the virtualethernet segment on the neighboring PE device. The PE device maintains atable or a list that includes the one or more virtual ethernet segmentsalong with their corresponding port identifier. The PE device receives amessage from a neighboring PE device that identifies a port on theneighboring PE device that has failed. Using the message, the receivingPE device can sort its local table and identify the affected virtualethernet segments that are associated with the failed port. In response,the receiving PE device can invalidate any locally stored virtualethernet segment routes that are associated with the failed port. The PEdevice can also initiate a new designated forwarder election process foreach of the affected virtual ethernet segments.

DETAILED DESCRIPTION

A computer network can include a system of hardware, software,protocols, and transmission components that collectively allow separatedevices to communicate, share data, and access resources, such assoftware applications. More specifically, a computer network is ageographically distributed collection of nodes interconnected bycommunication links and segments for transporting data betweenendpoints, such as personal computers and workstations. Many types ofnetworks are available, ranging from local area networks (LANs) and widearea networks (WANs) to overlay and software-defined networks, such asvirtual extensible local area networks (VXLANs), and virtual networkssuch as virtual LANs (VLANs) and virtual private networks (VPNs).

LANs typically connect nodes over dedicated private communications linkslocated in the same general physical location, such as a building orcampus. WANs, on the other hand, typically connect geographicallydispersed nodes over long-distance communications links, such as commoncarrier telephone lines, optical lightpaths, synchronous opticalnetworks (SONET), or synchronous digital hierarchy (SDH) links. LANs andWANs can include layer 2 (L2) and/or layer 3 (L3) networks and devices.

The Internet is an example of a public WAN that connects disparatenetworks throughout the world, providing global communication betweennodes on various networks. The nodes typically communicate over thenetwork by exchanging discrete frames or packets of data according topredefined protocols, such as the Transmission Control Protocol/InternetProtocol (TCP/IP). In this context, a protocol can refer to a set ofrules defining how the nodes interact with each other. Computer networksmay be further interconnected by intermediate network nodes, such asrouters, switches, hubs, or access points (APs), which can effectivelyextend the size or footprint of the network.

A service provider network can provide service to customer networks viaProvider Edge (PE) devices (e.g. routers or switches) that are locatedat the edge of the service provider network. Each PE device may beconnected directly to a Customer Edge (CE) device (e.g. host, router orswitch) located at the edge of a customer network. In other cases, anAccess Network (AN) provides connectivity (via Ethernet Virtual Circuits(EVC)) in order to interconnect PE and CE devices. In some instances,the AN can be an Ethernet Access Network (EAN) that can support EVCs byutilizing 802.1Q encapsulations. Alternatively, the AN can be a IP or aMPLS network that can support EVCs by utilizing Ethernet over IPencapsulation or Ethernet over MPLS encapsulation, respectively. The PEdevices in a service provider network may be connected by aMulti-Protocol Label Switching (MPLS) infrastructure that providesbenefits such as fast-reroute and resiliency. The PE devices may also beconnected by an IP infrastructure that utilizes Generic RoutingEncapsulation (GRE) tunneling or other IP tunneling between the PEdevices.

An Ethernet Virtual Private Network (EVPN) is a layer 2 virtual privatenetwork (VPN) technology built over a Packet Switched Network (PSN)(e.g. utilizing an MPLS/IP infrastructure). An EVPN instance includes CEdevices that are connected to PE devices that form the edge of the MPLSinfrastructure. An EVPN instance can include one or more broadcastdomains (e.g. one or more VLANs)that are assigned to a given EVPNinstance by the provider of the EVPN service. The PE devices providevirtual layer 2 bridged connectivity between the CE devices. A serviceprovider network can include multiple EVPN instances. EVPN providesadvanced multi-homing capabilities and uses Border Gateway Protocol(BGP) to distribute customer MAC address information over the core MPLSnetwork.

Ethernet Provider Backbone Bridging (PBB) can be combined with EVPN tocreate a PBB-EVPN. In PBB-EVPN, MAC-in-MAC tunneling is employed toimprove service instance and MAC address scalability in Ethernetnetworks. PBB-EVPN reduces the number of BGP MAC advertisement routes byaggregating Customer/Client MAC (C-MAC) address via Provider BackboneMAC address (B-MAC).

EVPN and PBB-EVPN can each provide a service provider network withsolutions for multipoint Ethernet services utilizing MPLS/IP networksand advanced multi-homing capabilities. For example, EVPN and PBB-EVPNcan each support single-homed devices, single-homed networks,multi-homed devices and multi-homed networks. A customer multi-homeddevice or a customer multi-homed network can tolerate certain networkfailures because the connection to two or more PE devices providesadditional redundancy. In all-active redundancy mode, all of the PEsattached to a customer multi-homed device/network are allowed to forwardtraffic to/from that customer device or customer network. Insingle-active redundancy mode, only a single PE (the designatedforwarder), among a group of PEs attached to a customer multi-homeddevice/network, is allowed to forward traffic to/from the customerdevice or customer network. In the event a failure occurs at the PEdevice that is the designated forwarder, a new designated forwarder canbe elected in order to maintain network connectivity.

In the case where a CE device/network is multi-homed to two or more PEdevices, the set of Ethernet links between the CE device and the PEdevices constitutes an Ethernet Segment (ES). In instances when an AN isused, a port (physical or logical (e.g. bundle)) on a PE device acts asa Network-to-Network Interface (NNI). In this context, NNIs are used toaggregate and interconnect customers to a PE device by utilizing accessEthernet Virtual Circuits (EVCs). An External NNI (ENNI) is used whenthe AN is built and operated by a third-party Service Provider. AnEthernet Segment that consists of EVCs instead of physical links isreferred to as a Virtual Ethernet Segment (vES).

The use of virtual Ethernet Segments can significantly expand thecapability of a single PE device. In the case of an ES, the PE islimited to having a single CE device connected to each of its ports,i.e. there is a one-to-one relationship between a CE device and aphysical/logical port (e.g. a bundle such as a 2x10GE bundle) on the PE.In the case of a vES, the PE device can be configured to provide serviceto thousands of customers over a common NNI that terminates access EVCsinterconnecting thousands of CE devices.

The disclosed technology addresses the need in the art for fastconvergence for failures of large scale virtual ethernet segments inEVPN and PBB-EVPN networks. Disclosed are systems, methods, andcomputer-readable storage media for providing fast convergence in theevent an NNI/ENNI failure is detected at a PE device. A description of aservice provider network, as illustrated in FIG. 1, is first disclosedherein. A discussion of fast convergence for failure of large scale vESin EVPN and PBB-EVPN will then follow, including examples and variationsas illustrated in FIGS. 2-4. The discussion concludes with a briefdescription of example devices, as illustrated in FIGS. 5 and 6A-B.These variations shall be described herein as the various embodimentsare set forth. The disclosure now turns to FIG. 1.

FIG. 1 illustrates a schematic block diagram of an example serviceprovider network 100 including nodes/devices interconnected by variousmethods of communication. The service provider network 100 can includeany number of provider edge (PE) devices such as PE1 104 and PE2 106.The PE devices PE1 104 and PE2 106 can communicate with each other overa Multi-Protocol Label Switching (MPLS) network 102. The serviceprovider network 100 can also include any number of Customer Edge (CE)devices such as CE1 108, CE2 110, CE3 112 and CE4 114. A CE device maybe a host, a router, or a switch. The PEs can provide virtual Layer 2bridged connectivity between the CEs.

Service provider network 100 can also include an Access Network (AN) 124that can provide connectivity between PE devices and CE devices. AN 124can be an Ethernet Access Network (EAN), a MPLS network, or an IPnetwork. In some instances, PE devices 104/106 and AN 124 can be builtand/or operated by a single service provider. Alternatively, PE devices104/106 and AN 124 can be built and/or operated by separate entities orby separate divisions associated with a service provider. Those skilledin the art will recognize that AN 124 can include additional networkcomponents that are not shown in FIG. 1.

Each PE device in the service provider network 100 can have one or moreports that can be used to provide network connectivity to the CE devicesvia AN 124. A port on a PE device can be a physical port such as a 10GEinterface or logical port such as a 2x10GE bundle. For example, PE1 104can have one or more physical or logical ports such asNetwork-to-Network Interface (NNI) 104 a. Likewise, PE2 106 can have oneor more physical or logical ports such as Network-to-Network Interface(NNI) 106 a. Each NNI can be associated with one or more EthernetVirtual Circuits (EVCs) such as EVC 116, EVC 118 a, EVC 118 b, EVC 120a, and EVC 120 b that are used by AN 124 to provide connectivity betweenPE and CE devices. When AN 124 is operated by a third-party serviceprovider, the ports on PE1 104 and PE2 106 can correspond to an ExternalNNI (ENNI).

A Virtual Ethernet Segment (vES) can include multiple EVCs. EVC 118 aand EVC 118 b together can make up vES 118. Similarly, EVC 120 a and EVC120 b together can make up vES 120. By utilizing EVCs, a single NNI porton a PE device can be configured to connect to multiple CE devices. Forexample, NNI 104 a can connect to CE1 108, CE2 110, and CE4 114 throughEVC 116, EVC 118 a, and EVC 120 b, respectively. Similarly, NNI 106 acan connect to CE3 112 through EVC 118 b and to CE4 114 through EVC 120a. Those skilled in the art will recognize that the number of devicesshown and the specific configuration is for the purpose of illustrationonly and is not intended to limit the scope of the present technology.In some embodiments, a switch can be used to aggregate multiple EVCsinto a single physical port on a PE device. For example, EVCs 116, 118a, and 120 b can each be coupled to a network switch (not shown) that isconnected to NNI 104 a. The configuration shown in service providernetwork 100 is for illustrative purposes and does not limit the presenttechnology. Configurations that include additional and/or differentcomponents and connections are contemplated herein.

Service provider network 100 can provide multipoint Ethernet service byutilizing EVPN or PBB-EVPN. EVPN and PBB-EVPN PEs can signal and learnMAC addresses of their corresponding CEs using Border Gateway Protocol.This can enable the PEs to learn what CEs or networks are single-homedor multi-homed.

When a CE is multi-homed, i.e. it is connected to more than one PE,there are two redundancy modes of operation. In all-active redundancymode, all of the PEs attached to a particular vES are allowed to forwardtraffic to/from that vES. In single-active redundancy mode, only asingle PE (the designated forwarder), among a group of PEs attached to avES, is allowed to forward traffic to/from the vES.

Turning back to service provider network 100, it can include bothsingle-homed and multi-homed CE devices and networks. For example, CE1108 is connected to PE1 104 through EVC 116. As illustrated, CE1 108 isnot connected to any other PE devices. Thus, CE1 108 can be classifiedas a single-homed device. That is, if a failure occurs on PE1 104 thatcauses NNI 104 a to fail, then CE1 108 would be left without networkconnectivity because it does not have any other connections to provideredundancy.

Alternatively, CE4 114 is a multi-homed device because it is connectedto PE1 104 through EVC 120 b and also to PE2 106 through EVC 120 a.Accordingly, PE1 104 and PE2 106 can function together in eitherall-active redundancy mode or in single-active redundancy mode withrespect to CE4 114. As mentioned above, each PE in a service providernetwork can advertise the MAC addresses and/or routes associated witheach of its ports. Thus, PE1 104 can advertise that vES 120 isassociated with its NNI 104 a. Likewise, PE2 can advertise that vES 120is associated with its NNI 106 a.

Service provider network 100 can also include multiple CE devices thatare part of a single customer network, such as network 122. A singlecustomer location may increase its redundancy by maintaining CE2 110 andCE3 112 which are each connected to different PE devices, PE1 104 andPE2 106, respectively. Network 122 is thus a multi-homed network. Amulti-homed network can receive the same redundancy benefits as amulti-homed device—e.g. the PE devices can operate in single-activeredundancy or in all-active redundancy.

In the event a failure occurs at a PE device that is associated with amulti-homed CE device, the system must converge efficiently to minimizenetwork down-time and avoid lost data packets. For example, PE1 104 andPE2 106 can operate in single-active redundancy mode with respect to CE4114 with PE1 104 as the designated forward. If a port failure occurs atPE1 104, it must alert PE2 106 (as well as any other PEs in the network)of the failure such that PE2 106 can commence routing network traffic toCE4 114 as soon as possible. However, because NNI 104 a can beassociated with thousands of Virtual Ethernet Segments, PE1 104 mustutilize an efficient method to alert all other PEs simultaneously ratherthan on a per route or per vES basis.

FIG. 2 illustrates an example method 200 for performing fast convergenceupon detecting a Provider Edge port failure in EVPN and PBB-EVPN. Themethod 200 begins at step 202 and proceeds to step 204 where a PE deviceconfigures a Virtual Ethernet Segment, such as vES 118 or vES 120discussed with respect to FIG. 1. As noted above, a single port (NNI orENNI) on a PE device can support thousands of Virtual Ethernet Segments.Therefore, this step can be repeated as necessary in order to configureall Virtual Ethernet Segments on each NNI of the PE device.

The method 200 proceeds to step 206 where the PE device advertises eachof the routes for the configured Virtual Ethernet Segments. In doing so,the PE can color, label, identify, map, or tag the route for the vESwith a port identifier. As used herein, the term color refers to theinclusion of additional information in the route advertising messagethat identifies the NNI or ENNI port that is associated with the route.In one embodiment, the PE can append or otherwise include the MediaAccess Control (MAC) address of the port that is associated with thevES. For example, if the MAC address for NNI 104 a on PE1 104 is AA BBCC DD EE FF, then this address could be included with the advertisingmessage for each of the vES routes on that port. That is, uponadvertising vES 116, vES 118, and vES 120, PE1 104 would include the MACaddress in each of the advertising messages. The PE device couldcontinue to do so for each vES configures on each of its ports. Notethat the MAC address is simply one example of an identifier for the NNIport. Those that are skilled in the art will recognize that otheridentifiers can be used as alternatives. The MAC address is used here asa non-limiting example for explanation purposes. Also note that theadvertising message transmitted in step 206 is designated with an “A”because it corresponds to the message that is received in step 304 ofmethod 300, discussed more fully below with respect to FIG. 3.

After the routes are advertised to the other PEs in the service providernetwork, the method continues to step 208 where the PE device monitorsfor any port failures. A port failure can include a failure of aphysical port or of a logical port. A port can correspond to an NNI oran ENNI on a PE device, as described with respect to FIG. 1. In someembodiments, a port failure can be detected by monitoring light levelsfor a transmit fault or a receive fault. If no port failure is detected,the method proceeds to step 212 where the PE returns to previousprocessing, which includes repeating method 200. Alternatively, if thePE detects that a particular port, e.g. an NNI or an ENNI, has failed,then the method proceeds to step 210.

At step 210, the PE can send a message to neighboring PE devices in theservice provider network that identifies the port failure. For example,the message can instruct other PEs to invalidate any routes that theyhave stored which are associated with the failed port. The port failuremessage can identify the port in the same manner as it was identified inthe previously disseminated route advertisements. That is, one manner toidentify the port failure is to utilize the MAC address of the failedport.

In the case of EVPN, the port failure message can be a specialmass-withdraw with the MAC address of the failed port encoded in theEthernet Segment Identifier (ESI) field. In one embodiment, an EthernetAuto-Discovery (A-D) BGP route with a type 3 ESI can be used with theMAC field set to the MAC address of the port and the 3-octet localdiscriminator field set to 0xFFFFFF. The mass-withdraw route can signalremote PEs to access a locally stored list of Virtual Ethernet Segmentsand initiate the mass-withdraw procedure for each vES associated withthe particular MAC address.

In the case of PBB-EVPN, the port failure message can be a BGP routewithdrawal corresponding to the MAC address of the failed port. In oneembodiment, when the MAC address of the NNI/ENNI port is used as BMACsource address, a withdrawal of the MAC advertisement BGP route for theNNI/ENNI's MAC can be used. In another , when a shared MAC is used asBMAC SA for all single-active vESs, then a re-advertisement of a BGP MACroute (for the shared BMAC) along with the field used to signalNNI/ENNI's color and along with MAC Mobility extended community can beused. Note that the port failure message discussed with respect to step210 is designated with a “B” and corresponds to the message that isreceived at step 308 of method 300, discussed more fully below withrespect to FIG. 3.

After the port failure message is sent at 210, the method continues tostep 212 where it returns to previous processing, which includesrepeating method 200.

FIG. 3 illustrates a second example method 300 for performing fastconvergence upon detecting a Provider Edge port failure in EVPN andPBB-EVPN. The method 300 begins at step 302 and proceeds to step 304where a PE device receives a message advertising routes for VirtualEthernet Segments. The message can be received by a remote PE in theservice provider network from a PE that is executing method 200discussed above. The message can include a route to a vES and it can becolored, labeled, tagged, identified, or associated with a particularidentifier. In one embodiment, the color can correspond to the MACaddress of the NNI or the ENNI port on the PE device that is advertisingthe route.

After receiving the message at 304, the method continues to 306 wherethe PE device can update its local table/list of Virtual EthernetSegments. FIG. 4 illustrates an example route table 400 that can beutilized to maintain the vES routes and their associated colors. Routetable 400 can include an entry that corresponds to each received vESroute advertisement. For each advertised vES, the table can include avES identifier, a color associated with the vES identifier, and a nexthop field that identifies the PE device that advertised the vES and itscolor. For example, the top row indicates that vES ‘A’ was colored as‘Blue’ at remote PE1. In addition, entries were made for routeadvertisements corresponding to vES ‘B’ and vES ‘ZZ’ which are each alsoassociated with color ‘Blue.’ Therefore, the table illustrates that eachof vES ‘A,’ vES ‘B,’ and vES ‘ZZ’ are associated with the same NNI onPE1 because they each have the same color. Likewise, vES ‘C’ and vES ‘D’also share an NNI because they are both colored with ‘Yellow’ by remotePE3. Note that vES ‘A’ is also associated with color ‘Red’ as advertisedby PE3, which means that vES ‘A’ is multi-homed to the port thatcorresponds to ‘Blue’ on PE1 and to the port that corresponds to ‘Red’on PE3. Those that are skilled in the art will recognize that routetable 400 is merely an example of a data structure that could be used tomaintain this information, and the present disclosure is not limited tothis embodiment. Similarly, the PE can store the route information ondifferent memory devices such as RAM, ROM, Flash, TCAM, etc.

After step 306, the method continues to step 308 where it receives amessage from a neighboring PE device indicating that a port failure hasoccurred. This message can correspond to a message sent by a PEexecuting method 200 discussed above at step 210. Accordingly, themessage can be colored with a unique port identifier that corresponds tothe failed port such as a MAC address of an NNI port. The PE device canreceive the message and decompose it to extract the appropriate “color”in order to properly index its locally stored route list or table.

The method continues to step 310 where the PE sorts the locally storedroute table/list to identify each vES that is associated with the portfailure. After identifying all of the affected vESs, the method cancontinue to step 312 where the PE can initiate a mass-withdraw andinvalidate (e.g. flush, withdraw, delete, remove) all affected routesthat are associated with the port (i.e. color) identified in themessage. For example, if the received port failure message was coloredas ‘Blue’ coming from PE1, then the local PE device would immediatelyinvalidate the routing entries associated with the impacted vESs: ‘A,’‘B,’ and ‘ZZ’.

The method continues to step 314 where the PE device determines if it isparticipating in any of the affected vESs. That is, the PE can determineif any of the affected Virtual Ethernet Segments is associated with alocal port. Returning to FIG. 1, if PE1 104 informs PE2 106 of a failureat NNI 104 a, then PE2 106 can determine that both vES 118 and vES 120are affected by the port failure and are associated with a local portthat is a non-designated forwarder for each affected vES. In response,the method can proceed to step 316 where a designated forwarder electionprocess is initiated for the affected vESs. The affected vESs may beconfigured in single-active redundancy mode in which the failed port wasthe designated forwarder. The PE device that is elected as a newdesignated forwarder for a given EVPN instance will unblock traffic forthat EVPN instance.

If the PE is not participating in any of the affected vESs, the methodcontinues to step 316 where the PE device resumes previous processing,which includes repeating method 300.

The ‘coloring’ of routes discussed in the example methods describedabove with respect to FIGS. 2 and 3 is used as a non-limiting examplefor explanation purposes. Other attributes, associations, tags, labelingmechanisms, identification mechanisms, mapping mechanisms are alsocontemplated herein. For example, routes can be marked with specificsymbols or characters to uniquely identify an associated NNI port on aPE device.

Example Devices

FIG. 5 illustrates an example network device 510 suitable for highavailability and failover. Network device 510 includes a master centralprocessing unit (CPU) 562, interfaces 568, and a bus 515 (e.g., a PCIbus). When acting under the control of appropriate software or firmware,the CPU 562 is responsible for executing packet management, errordetection, and/or routing or forwarding functions. The CPU 562 canaccomplish all these functions under the control of software includingan operating system and any appropriate applications software. CPU 562may include one or more processors 563 such as a processor from theMotorola family of microprocessors or the MIPS family ofmicroprocessors. In an alternative embodiment, processor 563 isspecially designed hardware for controlling the operations of networkdevice 510. In a specific embodiment, a memory 561 (such as non-volatileRAM and/or ROM) also forms part of CPU 562. However, there are manydifferent ways in which memory could be coupled to the system.

The interfaces 568 are typically provided as interface cards (sometimesreferred to as “line cards”). Generally, they control the sending andreceiving of data packets over the network and sometimes support otherperipherals used with the network device 510. Among the interfaces thatmay be provided are Ethernet interfaces, frame relay interfaces, cableinterfaces, DSL interfaces, token ring interfaces, and the like. Inaddition, various very high-speed interfaces may be provided such asfast token ring interfaces, wireless interfaces, Ethernet interfaces,Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POSinterfaces, FDDI interfaces and the like. Generally, these interfacesmay include ports appropriate for communication with the appropriatemedia. In some cases, they may also include an independent processorand, in some instances, volatile RAM. The independent processors maycontrol such communications intensive tasks as packet switching, mediacontrol and management. By providing separate processors for thecommunications intensive tasks, these interfaces allow the mastermicroprocessor 562 to efficiently perform routing computations, networkdiagnostics, security functions, etc.

Although the system shown in FIG. 5 is one specific network device ofthe present invention, it is by no means the only network devicearchitecture on which the present invention can be implemented. Forexample, an architecture having a single processor that handlescommunications as well as routing computations, etc. is often used.Further, other types of interfaces and media could also be used with therouter.

Regardless of the network device's configuration, it may employ one ormore memories or memory modules (including memory 561) configured tostore program instructions for the general-purpose network operationsand mechanisms for roaming, route optimization and routing functionsdescribed herein. The program instructions may control the operation ofan operating system and/or one or more applications, for example. Thememory or memories may also be configured to store tables such asmobility binding, registration, and association tables, etc.

FIG. 6A and FIG. 6B illustrate example system embodiments. The moreappropriate embodiment will be apparent to those of ordinary skill inthe art when practicing the present technology. Persons of ordinaryskill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 6A illustrates a conventional system bus computing systemarchitecture 600 wherein the components of the system are in electricalcommunication with each other using a bus 605. Exemplary system 600includes a processing unit (CPU or processor) 610 and a system bus 605that couples various system components including the system memory 615,such as read only memory (ROM) 670 and random access memory (RAM) 675,to the processor 610. The system 600 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 610. The system 600 can copy data from the memory615 and/or the storage device 630 to the cache 617 for quick access bythe processor 610. In this way, the cache can provide a performanceboost that avoids processor 610 delays while waiting for data. These andother modules can control or be configured to control the processor 610to perform various actions. Other system memory 615 may be available foruse as well. The memory 615 can include multiple different types ofmemory with different performance characteristics. The processor 610 caninclude any general purpose processor and a hardware module or softwaremodule, such as module 1 637, module 7 634, and module 3 636 stored instorage device 630, configured to control the processor 610 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 610 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction with the computing device 600, an inputdevice 645 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 635 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 600. The communications interface640 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 630 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 675, read only memory (ROM) 670, andhybrids thereof.

The storage device 630 can include software modules 637, 634, 636 forcontrolling the processor 610. Other hardware or software modules arecontemplated. The storage device 630 can be connected to the system bus605. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 610, bus 605, display 635, and soforth, to carry out the function.

FIG. 6B illustrates an example computer system 650 having a chipsetarchitecture that can be used in executing the described method andgenerating and displaying a graphical user interface (GUI). Computersystem 650 is an example of computer hardware, software, and firmwarethat can be used to implement the disclosed technology. System 650 caninclude a processor 655, representative of any number of physicallyand/or logically distinct resources capable of executing software,firmware, and hardware configured to perform identified computations.Processor 655 can communicate with a chipset 660 that can control inputto and output from processor 655. In this example, chipset 660 outputsinformation to output 665, such as a display, and can read and writeinformation to storage device 670, which can include magnetic media, andsolid state media, for example. Chipset 660 can also read data from andwrite data to RAM 675. A bridge 680 for interfacing with a variety ofuser interface components 685 can be provided for interfacing withchipset 660. Such user interface components 685 can include a keyboard,a microphone, touch detection and processing circuitry, a pointingdevice, such as a mouse, and so on. In general, inputs to system 650 cancome from any of a variety of sources, machine generated and/or humangenerated.

Chipset 660 can also interface with one or more communication interfaces690 that can have different physical interfaces. Such communicationinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods for generating, displaying,and using the GUI disclosed herein can include receiving ordereddatasets over the physical interface or be generated by the machineitself by processor 655 analyzing data stored in storage 670 or 675.Further, the machine can receive inputs from a user via user interfacecomponents 685 and execute appropriate functions, such as browsingfunctions by interpreting these inputs using processor 655.

It can be appreciated that example systems 600 and 650 can have morethan one processor 610 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, rackmount devices, standalone devices, and so on.Functionality described herein also can be embodied in peripherals oradd-in cards. Such functionality can also be implemented on a circuitboard among different chips or different processes executing in a singledevice, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims. Moreover, claimlanguage reciting “at least one of” a set indicates that one member ofthe set or multiple members of the set satisfy the claim.

We claim:
 1. A method comprising: receiving, at a first provider edge(PE) device, a port failure message from a second PE device, the messagecomprising a mass withdrawal message to remove all affected routesassociated with a port identifier for an interface of the second PEdevice; identifying a plurality of affected virtual Ethernet segmentsassociated with the port identifier for the interface of the second PEdevice; and removing, at the first PE device, any routes associated withat least one of the plurality of affected virtual Ethernet segments. 2.The method of claim 1, wherein the port identifier includes as mediaaccess control (MAC) address of the interface acting as network tonetwork interface (NNI), and (ii) a color or a tag applied by the firstPE device, the second PE device, or another PE device.
 3. The method ofclaim 2, further comprising maintaining, at the first PE device, a tablecomprising a mapping of the one or more virtual Ethernet segments to thecorresponding port identifier for the interface of the second PE device,wherein the table includes a plurality of virtual Ethernet segmentsassociated with the MAC address.
 4. The method of claim 1, furthercomprising maintaining, at the first PE device, a table comprising amapping of the one or more virtual Ethernet segments to thecorresponding port identifier for the interface of the second PE device,wherein the identifying comprising sorting the table.
 5. The method ofclaim 1, further comprising: configuring, when the port associated withthe at least one affected virtual Ethernet segment is a non-designatedforwarder, the port to be a designated forwarder, and initiating, whenthe at least one affected virtual Ethernet segment is associated with aport on the first PE device, a designated forwarder election process. 6.The method of claim 4, further comprising: identifying, based on thetable, a plurality of affected virtual Ethernet segments that areassociated with the port identifier for the interface of the second PEdevice; and initiating a designated forwarder election process for eachof the plurality of affected virtual Ethernet segments.
 7. The method ofclaim 1, wherein the at least one affected virtual Ethernet segment isassociated with at least one of a multi-homed customer edge (CE) deviceor a multi-homed network.
 8. A system, comprising: a processor; and acomputer-readable storage medium having stored therein instructionswhich, when executed by the processor, cause the processor to performoperations comprising: receiving, at a first provider edge (PE) device,a port failure message from a second PE device, the message comprising amass withdrawal message to remove all affected routes associated with aport identifier for an interface of the second PE device; identifying aplurality of affected virtual Ethernet segments associated with the portidentifier for the interface of the second PE device; and removing, atthe first PE device, any routes associated with at least one of theplurality of affected virtual Ethernet segments.
 9. The system of claim8, wherein the port identifier includes as media access control (MAC)address of the interface acting as network to network interface (NNI),and (ii) a color or a tag applied by the first PE device, the second PEdevice, or another PE device.
 10. The system of claim 9, the operationsfurther comprising maintaining, at the first PE device, a tablecomprising a mapping of the one or more virtual Ethernet segments to thecorresponding port identifier for the interface of the second PE device,wherein the table includes a plurality of virtual Ethernet segmentsassociated with the MAC address.
 11. The system of claim 8, theoperations further comprising maintaining, at the first PE device, atable comprising a mapping of the one or more virtual Ethernet segmentsto the corresponding port identifier for the interface of the second PEdevice, wherein the identifying comprising sorting the table.
 12. Thesystem of claim 8, the operations further comprising: configuring, whenthe port associated with the at least one affected virtual Ethernetsegment is a non-designated forwarder, the port to be a designatedforwarder, and initiating, when the at least one affected virtualEthernet segment is associated with a port on the first PE device, adesignated forwarder election process.
 13. The system of claim 12, theoperations further comprising: identifying, based on the table, aplurality of affected virtual Ethernet segments that are associated withthe port identifier for the interface of the second PE device; andinitiating a designated forwarder election process for each of theplurality of affected virtual Ethernet segments.
 14. The system of claim8, wherein the at least one affected virtual Ethernet segment isassociated with at least one of a multi-homed customer edge (CE) deviceor a multi-homed network.
 15. A non-transitory computer-readable storagemedium having stored therein instructions which, when executed by aprocessor, cause the processor to perform operations comprising:receiving, at a first provider edge (PE) device, a port failure messagefrom a second PE device, the message comprising a mass withdrawalmessage to remove all affected routes associated with a port identifierfor an interface of the second PE device; identifying a plurality ofaffected virtual Ethernet segments associated with the port identifierfor the interface of the second PE device; and removing, at the first PEdevice, any routes associated with at least one of the plurality ofaffected virtual Ethernet segments.
 16. The media of claim 15, whereinthe port identifier includes as media access control (MAC) address ofthe interface acting as network to network interface (NNI), and (ii) acolor or a tag applied by the first PE device, the second PE device, oranother PE device.
 17. The media of claim 16, the operations furthercomprising maintaining, at the first PE device, a table comprising amapping of the one or more virtual Ethernet segments to thecorresponding port identifier for the interface of the second PE device,wherein the table includes a plurality of virtual Ethernet segmentsassociated with the MAC address.
 18. The media of claim 15, theoperations further comprising maintaining, at the first PE device, atable comprising a mapping of the one or more virtual Ethernet segmentsto the corresponding port identifier for the interface of the second PEdevice, wherein the identifying comprising sorting the table.
 19. Themedia of claim 15, the operations further comprising: configuring, whenthe port associated with the at least one affected virtual Ethernetsegment is a non-designated forwarder, the port to be a designatedforwarder, and initiating, when the at least one affected virtualEthernet segment is associated with a port on the first PE device, adesignated forwarder election process.
 20. The media of claim 19, theoperations further comprising: identifying, based on the table, aplurality of affected virtual Ethernet segments that are associated withthe port identifier for the interface of the second PE device; andinitiating a designated forwarder election process for each of theplurality of affected virtual Ethernet segments.